Resource CodeSystem/FHIR Server from package fhir.r4.nhsengland.stu1#1.3.0 (62 ms)

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Source

{
  "resourceType" : "CodeSystem",
  "id" : "England-HTTPErrorCodes",
  "url" : "https://fhir.nhs.uk/CodeSystem/http-error-codes",
  "version" : "1.0.0",
  "name" : "EnglandHTTPErrorCodes",
  "title" : "England HTTP Error Codes",
  "status" : "draft",
  "date" : "2024-06-13",
  "publisher" : "NHS England",
  "contact" : [
    {
      "name" : "NHS England",
      "telecom" : [
        {
          "system" : "email",
          "value" : "interoperabilityteam@nhs.net",
          "use" : "work",
          "rank" : 1
        }
      ]
    }
  ],
  "description" : "A set of codes that identifies the HTTP Error Codes in response to a request.",
  "copyright" : "Copyright © 2023+ NHS England Licensed under the Apache License, Version 2.0 (the \\\"License\\\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at  http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \\\"AS IS\\\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at  https://www.hl7.org/fhir/license.html.",
  "caseSensitive" : true,
  "content" : "complete",
  "concept" : [
    {
      "code" : "SEND_BAD_REQUEST",
      "display" : "400: The API was unable to process the request.",
      "definition" : "The API has given a 400 response to the Senders request."
    },
    {
      "code" : "REC_BAD_REQUEST",
      "display" : "400: The Receiver was unable to process the request.",
      "definition" : "The Receiver has given a 400 response to the Senders request."
    },
    {
      "code" : "PROXY_BAD_REQUEST",
      "display" : "400: The Proxy was unable to process the request.",
      "definition" : "The Proxy has given a 400 response internally to the Senders request."
    },
    {
      "code" : "BAD_REQUEST",
      "display" : "400: The Server was unable to process the request.",
      "definition" : "The Server has given a 400 response to the Senders request."
    },
    {
      "code" : "SEND_UNAUTHORIZED",
      "display" : "401: The API deemed you unauthorized to make this request.",
      "definition" : "The API has given a 401 response to the Senders request."
    },
    {
      "code" : "REC_UNAUTHORIZED",
      "display" : "401: The Receiver deemed you unauthorized to make this request.",
      "definition" : "The Receiver has given a 401 response to the Senders request."
    },
    {
      "code" : "PROXY_UNAUTHORIZED",
      "display" : "401: The Proxy deemed you unauthorized to make this request.",
      "definition" : "The Proxy has given a 401 response internally to the Senders request."
    },
    {
      "code" : "UNAUTHORIZED",
      "display" : "401: The Server deemed you unauthorized to make this request.",
      "definition" : "The Server has given a 401 response to the Senders request."
    },
    {
      "code" : "SEND_FORBIDDEN",
      "display" : "403: Failed to authenticate with the API.",
      "definition" : "The API has given a 403 response to the Senders request."
    },
    {
      "code" : "REC_FORBIDDEN",
      "display" : "403: Failed to authenticate with the Receiver.",
      "definition" : "The Receiver has given a 403 response to the Senders request."
    },
    {
      "code" : "PROXY_FORBIDDEN",
      "display" : "403: Failed to authenticate with the Receiver.",
      "definition" : "The Proxy has given a 403 response to the Senders request."
    },
    {
      "code" : "FORBIDDEN",
      "display" : "403: Failed to Authenticate with the Server.",
      "definition" : "The Server has given a 403 response to the Senders request."
    },
    {
      "code" : "PROXY_NOT_FOUND",
      "display" : "404: The Proxy was unable to find the specified resource.",
      "definition" : "The Proxy has given a 404 response to the Senders request."
    },
    {
      "code" : "REC_NOT_FOUND",
      "display" : "404: The Receiver was unable to find the specified resource.",
      "definition" : "The Receiver has given a 404 response to the Senders request."
    },
    {
      "code" : "NOT_FOUND",
      "display" : "404: The Server was unable to find the specified resource.",
      "definition" : "The Server has given a 404 response to the Senders request."
    },
    {
      "code" : "SEND_METHOD_NOT_ALLOWED",
      "display" : "405: This API doesnt allow this method.",
      "definition" : "The API has given a 405 response to the Senders request."
    },
    {
      "code" : "REC_METHOD_NOT_ALLOWED",
      "display" : "405: The Receiver doesnt allow this method.",
      "definition" : "The Receiver has given a 405 response to the Senders request."
    },
    {
      "code" : "PROXY_METHOD_NOT_ALLOWED",
      "display" : "405: The Proxy doesnt allow this method.",
      "definition" : "The Proxy has given a 405 response to the Senders request."
    },
    {
      "code" : "METHOD_NOT_ALLOWED",
      "display" : "405: This method is not allowed.",
      "definition" : "The Server has given a 405 response to the Senders request."
    },
    {
      "code" : "SEND_NOT_ACCEPTABLE",
      "display" : "406: Senders message had an incorrect content type defined for a response.",
      "definition" : "The API has given a 406 response to the Senders request."
    },
    {
      "code" : "REC_NOT_ACCEPTABLE",
      "display" : "406: Message had an incorrect content type defined for a response.",
      "definition" : "The Server has given a 406 response to the Senders request."
    },
    {
      "code" : "NOT_ACCEPTABLE",
      "display" : "406: Senders message had an incorrect content type defined for a response.",
      "definition" : "The Server has given a 406 response to the Senders request."
    },
    {
      "code" : "REC_TIMEOUT",
      "display" : "408: The request timed out to the receiver.",
      "definition" : "The Receiver has given a 408 resonse to the Senders request"
    },
    {
      "code" : "PROXY_TIMEOUT",
      "display" : "408: The request timed out internally.",
      "definition" : "The Proxy has given a 408 response internally to the Senders request."
    },
    {
      "code" : "TIMEOUT",
      "display" : "408: The request timed out.",
      "definition" : "The Server has given a 408 response to the Senders request."
    },
    {
      "code" : "SEND_CONFLICT",
      "display" : "409: The API identified a conflict.",
      "definition" : "The API has given a 409 response to the Senders request."
    },
    {
      "code" : "REC_CONFLICT",
      "display" : "409: The Receiver identified a conflict.",
      "definition" : "The Receiver has given a 409 response to the Senders request."
    },
    {
      "code" : "PROXY_CONFLICT",
      "display" : "409: The Proxy identified a conflict.",
      "definition" : "The Proxy has given a 409 response to the Senders request."
    },
    {
      "code" : "CONFLICT",
      "display" : "409: The Server identified a conflict.",
      "definition" : "The Server has given a 409 response to the Senders request."
    },
    {
      "code" : "REC_UNSUPPORTED_MEDIA_TYPE",
      "display" : "415: The request is in an unsupported format.",
      "definition" : "The Receiver has given a 415 response to the Senders request."
    },
    {
      "code" : "UNSUPPORTED_MEDIA_TYPE",
      "display" : "415: The request is in an unsupported format.",
      "definition" : "The Receiver has given a 415 response to the Senders request."
    },
    {
      "code" : "SEND_UNPROCESSABLE_ENTITY",
      "display" : "422: Message was not malformed but deemed unprocessable by the API.",
      "definition" : "The API has given a 422 response to the Senders request."
    },
    {
      "code" : "REC_UNPROCESSABLE_ENTITY",
      "display" : "422: Message was not malformed but deemed unprocessable by the Receiver.",
      "definition" : "The Receiver has given a 422 response to the Senders request."
    },
    {
      "code" : "PROXY_UNPROCESSABLE_ENTITY",
      "display" : "422: Message was not malformed but deemed unprocessable by the Proxy.",
      "definition" : "The Proxy has given a 422 response to the Senders request."
    },
    {
      "code" : "UNPROCESSABLE_ENTITY",
      "display" : "422: Message was not malformed but deemed unprocessable by the server.",
      "definition" : "The Server has given a 422 response to the Senders request."
    },
    {
      "code" : "PROXY_TOO_MANY_REQUESTS",
      "display" : "429: Too many requests have been made by this source to the Proxy in a given amount of time.",
      "definition" : "The Proxy has given a 429 response internally to the Senders request."
    },
    {
      "code" : "SEND_TOO_MANY_REQUESTS",
      "display" : "429: Too many requests have been made by this source to the API in a given amount of time.",
      "definition" : "The API has given a 429 response to the Senders request."
    },
    {
      "code" : "TOO_MANY_REQUESTS",
      "display" : "429: Too many requests have been made by this source in a given amount of time.",
      "definition" : "The Server has given a 429 response to the Senders request."
    },
    {
      "code" : "REC_SERVER_ERROR",
      "display" : "500: The Receiver has encountered an error processing the request.",
      "definition" : "The Receiver has given a 500 response to the Senders request."
    },
    {
      "code" : "PROXY_SERVER_ERROR",
      "display" : "500: The Proxy has encountered an error processing the request.",
      "definition" : "The Proxy has given a 500 response to the Senders request."
    },
    {
      "code" : "SERVER_ERROR",
      "display" : "500: The Server has encountered an error processing the request.",
      "definition" : "The Server has given a 500 response to the Senders request."
    },
    {
      "code" : "SEND_NOT_IMPLEMENTED",
      "display" : "501:The Request was not recognized by the API.",
      "definition" : "The API has given a 501 response to the Senders request."
    },
    {
      "code" : "REC_NOT_IMPLEMENTED",
      "display" : "501: The Request was not recognized by the Receiver.",
      "definition" : "The Receiver has given a 501 response to the Senders request."
    },
    {
      "code" : "PROXY_NOT_IMPLEMENTED",
      "display" : "501: The Request was not recognized by the Proxy.",
      "definition" : "The Proxy has given a 501 response to the Senders request."
    },
    {
      "code" : "NOT_IMPLEMENTED",
      "display" : "501: The Request was not recognized by the server.",
      "definition" : "The Server has given a 501 response to the Senders request."
    },
    {
      "code" : "PROXY_UNAVAILABLE",
      "display" : "503: An internal component is unavailable",
      "definition" : "The Proxy has given a 503 response internally to the Senders request."
    },
    {
      "code" : "REC_UNAVAILABLE",
      "display" : "503: The Receiver is currently unavailable.",
      "definition" : "The Receiver has given a 503 response to the Senders request."
    },
    {
      "code" : "UNAVAILABLE",
      "display" : "503: The Server is currently unavailable.",
      "definition" : "The Receiver has given a 503 response to the Senders request."
    }
  ],
  "text" : {
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.